Skip to content

Adding a new exception code/message, testing backup exceptions#692

Closed
jadunham1 wants to merge 1 commit intoapache:trunkfrom
jadunham1:feature/dd_handle_exception
Closed

Adding a new exception code/message, testing backup exceptions#692
jadunham1 wants to merge 1 commit intoapache:trunkfrom
jadunham1:feature/dd_handle_exception

Conversation

@jadunham1
Copy link
Copy Markdown
Contributor

The backup client bad responses have different XML responses than the others.
<ns0:Status xmlns:ns0="http://oec.api.opsource.net/schemas/general">
ns0:operationEnable Backup for Server/ns0:operation
ns0:resultERROR/ns0:result
ns0:resultDetailCloud backup for this server is already enabled or being enabled (state: NORMAL)./ns0:resultDetail
ns0:resultCodeREASON_550/ns0:resultCode
/ns0:Status

I added in handling for this and making it easier to create new bad xml elements in case there are more later on.
Added tests to test the bad handling in the backup client

@jadunham1 jadunham1 closed this Feb 6, 2016
@jadunham1 jadunham1 deleted the feature/dd_handle_exception branch February 6, 2016 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant